Token based new digital cash protocols

ABSTRACT

Digital cash token protocols employ two pairs of private and public keys. Each public key is certified separately and the protocols do not use any blind signature schemes. As a result, the digital cash token protocols provide strong protection of user privacy by using two certified public keys instead of a blind signature. One pair of certified keys consists of one master user private key and one master user public key. A second pair of certified keys consists of one pseudonym user private key and one pseudonym user public key. The use of a master key pair and a pseudonym key pair circumvents the need for blind signatures. As a result, the proposed protocols do not require blind signatures and do not add additional overhead and security requirements necessitated by conventional blind signature schemes. The protocols use public key protocols and digital signatures and symmetric key protocols, which may be readily implemented in standard information security based systems based on cryptographic constructs. In addition, the protocols may be deployed in mobile, off-line, and on-line settings.

TECHNICAL FIELD

This invention relates to digital cash, and more specifically to digital cash tokens using more than one user public key.

BACKGROUND

In the near future digital cash will come into wider use and it is expected that people will use the Internet to make digital cash payments for their purchases. Electronic transactions should be convenient, reliable, accurate, and resistant to fraud. Certain electronic transactions also should protect the privacy of payees. For example, a customer purchasing a service from a vendor over a network should be able to pay for the service in an electronic transaction without revealing their identity.

Some schemes using on-line banking may prevent double spending by checking each coin against reuse during the time of payment on-line rather than detecting double spending afterwards. However, on-line banking is obviously not suitable for micro-payments of the average consumer. Banks are too few compared with the vast number of small cash transactions that would need to be processed if average consumer transactions were to be supported. Processing on-line requests for such transactions will result in banks becoming serious bottlenecks to handle these transactions.

Blind signature systems that use off-line digital cash techniques have high system complexity. In some other conventional techniques, a coin has a data size that is too big to be economically used since the coin contains a large number of challenge terms to detect cheating. In addition, some techniques also require using complex challenge-response interactions between the payer and payee for each coin spent. Again, such complex schemes are also not suitable for micro payments.

Some systems have implemented digital coins that are both secure (in the bank's interest) and afford a heightened assurance of consumer privacy by providing some anonymity to users with respect to both merchants and banks. Informally, a digital cash scheme is referred to as unconditionally blind or anonymous if the bank that issues a coin is unable to determine, either at the time of withdrawal or later upon examining circulating or deposited coins, which coin was withdrawn by which user. In a unconditionally blind scheme, the user can withdraw money from the bank, spend it at a merchant, and be confident that when the merchant deposits the money at the bank, the bank will not be able to recognize the money as the same cash given to the user.

However, researchers have observed that unconditional anonymity in payment systems might be exploited to facilitate crimes like blackmail. In addition, there is a fear that such schemes of unconditional anonymity may be abused to perfect crimes of money laundering and kidnapping because this system can make the flow of cash completely untraceable. This observation has spurred research into the idea of making anonymity in payment systems conditional, and, in particular, revocable by a third party. This notion is referred to as a trustee-based coin tracing.

One trustee-based tracing scheme is based on a blind Schnorr-like signature scheme that involves use of interactive proofs between trustees and the bank. Another trustee-based tracing scheme is based on blind RSA signatures, but makes use of a cut-and-choose protocol that results in a scheme that is flexible. Although this scheme may be somewhat flexible, it has rather large coin sizes and computational requirements.

According to another scheme that makes use of a blind signature, a user requests a pseudonym and registration information from a trustee. The user presents this registration information to the bank, and incorporates the information into the coins that are withdrawn.

Another scheme makes use of blind DSS signatures. In this scheme, signing and anonymity revocation may be conducted by differing quorums of trustees. However, the scheme is implemented on-line only and is rather computationally intensive for most operations.

A slightly different approach to trustee-based tracing is a system based on blind Schnorr signatures in which a user transfers funds from a non-anonymous to an anonymous account where a trustee is capable of linking the two accounts. The chief disadvantage of this approach is that once the two accounts are linked, anonymity is eliminated.

Another approach is based on blind Schnorr signatures in which the trustee is off-line. This system is complex and involves well over a dozen modular exponentiations by the user at each coin withdrawal. Later developments have reduced the computational required in the withdrawal protocol, as well as the database search requirements in owner tracing. However, the withdrawal protocol still requires over a dozen modular exponentiations on the part of the user.

The use of blinding alone that protects the anonymity of the customer is not sufficient to safeguard against certain types of fraud. For example, a customer can submit a blinded nonce (a nonce is a piece of data that, for practical purposes, is used only once, for example, a random number) to the certification authority along with $20, receive the blinded certificate, un-blind it, and then submit the un-blinded certificate as being worth $100. This is possible because the certification authority never really sees the actual certificate it is signing because of the blinding factor. Thus, although blinding alone protects privacy, it does not by itself provide adequate reliability against fraud and misuse.

Another problem of blind signature it is a homomorphism, i.e., Sign(kx)=Sign(k)Sign(x). It is possible to create pairs r, Sign(r) for a random message r. More precisely, anyone can choose Sign(r) at random and then compute r as the function Sign−1 which is known publicly. The basic idea is as follows. Customer C chooses a message x which is going to be the coin. C also generates a pair, k and Sign(k), for a random number k. C sends the product kx to a bank B which computes Sign(kx). B then sends Sign(kx) to C, using, for instance, a public encryption scheme provided by C (using some session key exchanged between C and B using a Diffie-Hellman session) or some other form of communication (e.g., delivery on a diskette transported by an armored carrier). C may then compute Sign(x) by dividing Sign (kx) by Sign (k). The pair (x, Sign(x)) is now redeemable by B at a value usually determined by the signature being used, and B cannot recognize C when some payee P presents (x, Sign(x)) (since the knowledge of kx does not allow practical recognition of x nor of Sign(x)).

A problem with this approach is that a signature scheme with such properties is not secure. This scheme provides that (1) it is easy to forge signatures on random messages, and (2) after seeing the signatures on two messages x1 and x2, it is easy to compute the signature on the message x=x1x2. In order to overcome this problem, valid messages are required to have a special “structure” (e.g., the message x must be encoded using the PKCS#1 standard for digital signature). The hope is that messages with this structure are sparse and hard to forge even given properties (1) and (2) (since messages with that structure will not appear with a significant probability). However, this is simply a hope and is not a proven mathematical property of the signature scheme or of the encoding. The drawback is that it may be possible to discover an algorithm to forge messages even when we restrict them to this structured sparse set.

Schemes that use virtual accounts have several problems. For example, some virtual accounts do not provide adequate privacy of the user, while others are complex requiring a blind signature to protect the privacy of the user. Still other embodiments have the bank storing encrypted pseudonym corresponding to the user identification which makes linking identity to the pseudonym easy either by cooperation or leakage of the secret key of the issuer. Accordingly, the privacy of all users can be catastrophically destroyed. In addition, there is a problem of proving the ownership of the user identity between the user and the bank.

SUMMARY

In one general aspect, a system for implementing a digital cash token protocol comprises: a user having two pairs of user keys, one pair linked to the real identity of the user, and a second pair linked to the pseudonym identity of the user, a bank to receive a request for an amount of digital cash from the user and generate a request for a digital cash token corresponding to the requested amount; and an issuer of digital cash to issue the digital cash token in response to the request from the bank, where the first pair of keys is used to authenticate the user with the bank and to encrypt information sent to the user from the bank and the second pair of keys is used to authenticate the user with the issuer of digital cash and to encrypt information sent to the user from the issuer of digital cash. The first pair may include a master public key and a master secret key and the second pair includes a pseudonym public key and a pseudonym secret key. No link is provided between the master public key and the pseudonym public key to determine the real identity of a user associated with a pseudonym. No link is provided between the master public key and the issued digital cash token, and the master public key is not used for payments in order to maintain user privacy.

The system also may include a certificate authority to certify the pseudonym public key of a user given the master public key of the user and a user identification. Each public key is certified by the certificate authority using a separate certificate. The user may transfer the issued digital cash token to another user that has a certified pseudonym public key. The certificate authority stores the pseudonym public key in correspondence to a user id or the master public key and issues a license for the pseudonym public key in response to a request which is signed by the master private key of the user. The certificate authority reveals the identity of the owner of a pseudonym public key if there is any misuse of digital cash token.

The master keys may be used to generate digital signatures for authentication with the certificate authority and the bank. The pseudonym keys may be used to generate digital signatures for authentication with the issuer of digital cash.

The issuer of digital cash tokens issues a digital cash license to the user and stores information related to the issued digital cash token. The stored information related to the issued digital token may include a random number.

In another general aspect, a digital cash issuing system for a user has two pairs of user keys, one pair linked to a real identity of the user, and a second pair linked to a pseudonym identity of the user. The system comprises: an input to receive to receive a request from a user for a digital cash license, to receive a request from a bank for a digital cash token, and to receive the digital cash token and a challenge as a request for payment from a shop; a processor to process the user request and issue the digital cash license for a pseudonym of the user; to generate and issue the digital cash token in response to the bank request; to process a request form payment from a shop including the received digital cash token and challenge and issue a payment to the shop in response to the shop request; and an output to send the digital cash license to the user, the digital cash token to the bank, the payment to the shop, where the second pair of keys is used to authenticate the user with the digital cash system and to encrypt information sent to the user from the digital cash system. The first pair may include a master public key and a master secret key and the second pair includes a pseudonym public key and a pseudonym secret key. No link is provided between the master public key and the pseudonym public key to determine the real identity of a user associated with a pseudonym. No link is provided between the master public key and the issued digital cash token, and the master public key is not used for payments in order to maintain user privacy.

Each public key may be certified by a certificate authority using a separate certificate. The user may transfer the issued digital cash token to another user that has a certified pseudonym public key. Pseudonym keys are used to generate digital signatures for authentication with the digital cash system. The processor may send a request to a certificate authority to reveal the identity of the owner of a pseudonym public key if there is any misuse of the digital cash token.

The processor is configured to generate the digital cash token by determining an amount of digital cash and a random number which are signed with a secret key of the digital cash system and storing the random number. The processor also is configured to processes the request for payment by verifying the user pseudonym secret key and determine if the random number of the digital cash token is stored.

In yet another general aspect, a method for implementing a digital cash protocol for a user having two pairs of user keys, one pair linked to the real identity of the user including a master public key (mPKU) and a master secret key (mSKU), and a second pair linked to the pseudonym identity of the user including a pseudonym public key (pPKU) and a pseudonym secret key (pSKU), in a system including a certificate authority, a bank of the user, an issuer of digital cash tokens, and a shop, the method comprises: registering a user with the certificate authority to store the pPKU in connection with a user id (UID) and the mPKU; issuing a license for the pPKU in response to a request from the user for digital currency which is signed by the mPKU; generating a license by the issuer of digital cash tokens for the pPKU of a registered user; sending a request for an amount of digital cash to the bank from the user including the pPKU; sending a request for a digital cash token in the requested amount from the bank to the digital cash tokens issuer; issuing the digital cash token in response to a request from the bank; and providing the digital cash token to the user for use as digital currency, where the digital cash token includes the amount and a random number stored by the digital cash token issuer.

The method may further include providing no link between the mPKU and the pPKU to determine the real identity of a user associated with a pseudonym.

The method may further include providing no link between the mPKU and the issued digital cash token, and the mPKU is not used for payments in order to maintain user privacy.

The method may further include certifying each public key by a certificate authority using a separate certificate.

The method may further include transferring the issued digital cash token from the user to another user that has a certified pseudonym public key.

The method may further include generating digital signatures for authentication with the digital cash system using the pseudonym keys.

The method may further include revealing the identity of the user associated with the pPKU if there is any misuse of the digital cash token.

The method may further include: providing the digital cash token and digital token issuer license from the user to a shop as a request for payment of an amount; challenging the request for payment from the user; signing the challenge by the user with the pSKU; sending the digital token and the signed challenge to the digital cash token for payment of the amount; verifying the request; and paying the amount, wherein verifying the request for payment includes verifying the pSKU and determining if the random number of the digital cash token is stored.

Other features will be apparent from the description, the drawings, and the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 shows an exemplary system network diagram for implementing the digital cash token protocol.

FIG. 2 is an exemplary user registration protocol according to the first embodiment.

FIG. 3 is an exemplary user registration process part 1 according to the first embodiment.

FIG. 4 is an exemplary user registration process part 2 according to the first embodiment.

FIG. 5 is an exemplary withdrawal protocol according to the first embodiment.

FIG. 6 is an exemplary withdrawal process part 1 according to the first embodiment.

FIG. 7 is an exemplary withdrawal process part 2 according to the first embodiment.

FIG. 8 is an exemplary withdrawal process part 3 according to the first embodiment.

FIG. 9 is an exemplary payment protocol according to the first embodiment.

FIG. 10 is and exemplary payment process part 1 according to the first embodiment.

FIG. 11 is an exemplary payment process part 2 according to the first embodiment.

FIG. 12 is an exemplary payment process part 3 according to the first embodiment.

FIG. 13 is an exemplary withdrawal protocol according to the second embodiment.

FIG. 14 is an exemplary withdrawal process part 1 according to the second embodiment.

FIG. 15 is an exemplary withdrawal process part 2 according to the second embodiment.

FIG. 16 is an exemplary withdrawal process part 3 according to the second embodiment.

FIG. 17 is an exemplary withdrawal protocol according to the third embodiment.

FIG. 18 is an exemplary withdrawal process part 1 according to the third embodiment.

FIG. 19 is an exemplary withdrawal process part 2 according to the third embodiment.

FIG. 20 is an exemplary withdrawal process part 3 according to the third embodiment.

FIG. 21 is an exemplary withdrawal process part 4 according to the third embodiment.

FIG. 22 is an exemplary withdrawal process part 5 according to the third embodiment.

FIG. 23 is an exemplary payment protocol according to the third embodiment.

FIG. 24 is an exemplary payment process part 1 according to the third embodiment.

FIG. 25 is an exemplary payment process part 2 according to the third embodiment.

FIG. 26 is an exemplary payment process part 3 according to the third embodiment.

FIG. 27 is an exemplary payment process part 4 according to the third embodiment.

FIG. 28 is an exemplary user registration Protocol according to the fourth embodiment.

FIG. 29 is an exemplary user registration process part 1 according to the fourth embodiment.

FIG. 30 is an exemplary user registration process part 2 according to the fourth embodiment.

FIG. 31 is an exemplary withdrawal protocol according to the fourth embodiment.

FIG. 32 is an exemplary withdrawal process part 1 according to the fourth embodiment.

FIG. 34 is an exemplary withdrawal process part 3 according to the fourth embodiment.

FIG. 35 is an exemplary withdrawal protocol according to the fifth embodiment.

FIG. 36 is an exemplary withdrawal process part 1 according to the fifth embodiment.

FIG. 37 is an exemplary withdrawal process part 2 according to the fifth embodiment.

FIG. 38 is an exemplary withdrawal process part 3 according to the fifth embodiment.

FIG. 39 is an exemplary withdrawal protocol according to the sixth embodiment.

FIG. 40 is an exemplary withdrawal process part 1 according to the sixth embodiment.

FIG. 41 is an exemplary withdrawal process part 2 according to the sixth embodiment.

FIG. 42 is an exemplary withdrawal process part 3 according to the sixth embodiment.

FIG. 43 is an exemplary withdrawal process part 4 according to the sixth embodiment.

FIG. 44 is an exemplary withdrawal process part 5 according to the sixth embodiment.

FIG. 45 is an exemplary payment protocol according to the seventh and eighth embodiment.

FIG. 46 is an exemplary payment process part 1 according to the seventh and eighth embodiment.

FIG. 47 is an exemplary payment process part 2 according to the seventh and eighth embodiment.

FIG. 48 is an exemplary payment process part 3 according to the seventh and eighth embodiment.

FIG. 49 is an exemplary payment process part 4 according to the seventh and eighth embodiment.

FIG. 50 is an exemplary payment protocol according to the ninth embodiment.

FIG. 51 is an exemplary payment process part 1 according to the ninth embodiment.

FIG. 52 is an exemplary payment process part 2 according to the ninth embodiment.

FIG. 53 is an exemplary payment process part 3 according to the ninth embodiment.

FIG. 54 is an exemplary payment process part 4 according to the ninth embodiment.

FIG. 55 is an exemplary payment process part 5 according to the ninth embodiment.

FIG. 56 is an exemplary withdrawal protocol according to the tenth embodiment.

FIG. 57 is an exemplary withdrawal process part 1 according to the tenth embodiment.

FIG. 58 is an exemplary withdrawal process part 2 according to the tenth embodiment.

FIG. 59 is an exemplary withdrawal process part 3 according to the tenth embodiment.

FIG. 60 is an exemplary payment protocol according to the tenth embodiment.

FIG. 61 is an exemplary payment process part 1 according to the tenth embodiment.

FIG. 62 is an exemplary payment process part 2 according to the tenth embodiment.

FIG. 63 is an exemplary payment process part 3 according to the tenth embodiment.

FIG. 64 is an exemplary payment process part 4 according to the tenth embodiment.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION Overview

Digital cash token protocols described below employ two pairs of private and public keys. Each public key is certified separately and the protocols do not use any blind signature schemes. As a result, the digital cash token protocols described herein provide strong protection of the user privacy by using two certified public keys instead of a blind signature.

One pair of certified keys consists of one master user private key and one master user public key. A second pair of certified keys consists of one pseudonym user private key and one pseudonym user public key. The use of a master key pair and a pseudonym key pair circumvents the need for blind signatures. As a result, the proposed protocols do not require blind signatures. Therefore, the protocols herein do not add additional overhead and security requirements necessitated by conventional blind signature schemes. The protocols use public key protocols, digital signatures and symmetric key protocols, which may be readily implemented in standard information security based systems based on cryptographic constructs. In addition, the protocols may be deployed in off-line and on-line setting.

The protocols described utilize the following entities: (i) a certificate authority, (ii) a user's bank, (iii) an issuer of digital cash, and (iv) a shop and (v) the shop's bank.

The certificate authority has storage to store a pseudonym public key in correspondence to a user id and/or master public key, issues a license for the pseudonym public key in response to a request which is signed by the master private key of the user. The certificate authority reveals the identity of the owner of a pseudonym public key if there is any misuse of digital cash tokens or fraud.

The user's bank holds the user's account with his ID, and the certified user's maser public key which is used to authenticate a user.

The issuer of digital cash tokens has a storage space for each registered user which is known under one or more pseudonyms, issues digital cash tokens in response to a request from the user, and stores information related to the issued digital cash tokens. The type of stored information about a digital cash tokens differs depending on whether traceable or untraceable digital cash tokens are being issued.

As shown in FIG. 1, a system for implementing the protocols includes a number of entities (e.g., a user, a certificate authority, a digital cash issuer, a user bank, a shop bank, and a shop).

Each of these entities may send and receive data via any number of communications paths. Each entity may include one or more processing devices, such as, for example, a general or special-purpose computer, such as a processor, a microprocessor, a microcomputer, a personal computer (“PC”), a workstation, a mainframe, a server, a laptop, a mobile communications device/phone, a personal digital assistant (“PDA”), an on-board (i.e., vehicle-mounted) computer, or a combination of two or more of these devices capable of responding to, generating, and/or executing instructions in a defined manner. The processing device may include or be associated with any number of other devices, components, and/or peripherals, such as additional computing devices, memory/storage devices, input devices, output devices, user interfaces, and/or communications interfaces.

Each entity also may include one or more software applications including, for example, encryption decryption software, signature generating software, key generating software, random number generating software, signature verification software, in addition to other system and operating system software loaded to command and direct the processing device. Software applications may be implemented as a computer program, a piece of code, an instruction, or some combination thereof, for independently or collectively instructing the processing device to interact and operate as desired.

The applications may be embodied permanently or temporarily in any type of machine, component, physical or virtual equipment, storage medium, or propagated signal wave capable of providing instructions to the processing device. In particular, the applications may be stored on a storage medium or device including volatile and non-volatile (e.g., a read only memory (ROM), a random access memory (RAM), a flash memory, a floppy disk, a hard disk, a tape, a DROM, a flip-flop, a register, an SRAM, DRAM, PROM, EPROM, OPTROM, EEPROM, NOVRAM, or RAMBUS), such that if the storage medium or device is read by the processing device, the specified steps, processes, and/or instructions are performed.

The processing device also may include one or more communications interfaces that allow the processing device to send and receive information using the communications paths. The communications paths may be configured to send and receive signals (e.g., electrical, electromagnetic, or optical) that convey or carry data streams representing various types of analog and/or digital data. For example, the communications paths may be implemented using various communications media and one or more networks comprising one or more network devices (e.g., servers, routers, switches, hubs, repeaters, and storage devices). The one or more networks may include a local area network (LAN), a wide area network (WAN), a plain old telephone service (POTS) network, a digital subscriber line (DSL) network, an integrated services digital network (ISDN), a synchronous optical network (SONNET), or a combination of two or more of these networks. In addition, the communications paths may include one or more wireless links (e.g., cellular, mobile, GSM, CDMA, TDMA, and satellite) that transmit and receive electromagnetic signals, such as, for example, radio, infrared, and microwave signals, to convey information. Because the communications paths may cover any number of networks and media, generally, they are considered unsecured.

The user may be any entity (person, group, business, government and/or organization) that requires the issuance of digital cash for use a payment to a shop. The certificate authority comprises a storage device, a signature verifying program, an encryption program, a decryption program, and a signature generating program. The user may include a processing device, a storage device, an encryption program, a decryption program, a signature verifying program and a key generating program and a signature generating program.

The digital cash issuer provides digital currency or digital cash tokens for use by the user as payment to a shop. The issuer may include a processing device, a storage device, an encryption program, a decryption program, a signature generating program, a signature verifying program, and a random number generating program.

The user's bank may include a processing device, a storage device, a signature verifying program encryption program, a decryption program, and a signature generating program.

The shop may include a processing device, a storage device, a signature verifying program encryption program, a decryption program, a signature generating program, a random number generating program and a time generating program.

Each of the exemplary embodiments for traceable tokens, described in detail below include at least three primary procedures: a user registration procedure; a withdrawal procedure (e.g., an electronic cash issuing procedure); and a payment procedure. The non-traceable embodiment includes two primary procedures: a withdrawal procedure, and a payment procedure.

In the following description, PKy denotes the public key of the entity y, Sky denotes the private key of the entity y, mPKy and mSKy denotes the master public and private key of entity y respectively, pPKy and pSKy denotes the pseudonym public and private key of entity y respectively, PKy(.) indicates that the quantity between parenthesis is encrypted using the public key of entity y, Sky(.) indicates that the quantity between parenthesis is encrypted using the private key of entity y, and [.]_(SKy) indicates that the quantity between square brackets is signed by the private key of entity y. The user public key PKC is known to all entities. The master public key mPKU is known to all entities. The issuer public key PKI is known to all entities. The bank's public key PKB are known to all entities. The shop public key PKS is known to all entities.

First Embodiment (1) User Registration Procedure

FIGS. 2, 3, and 4 show the diagrammatic representation of the registration protocol. Referring to FIG. 3, the user key generating program generates a pseudonym public key and a pseudonym secret key. The signature generating program then signs the pseudonym public key and the user real identification using the user's master secret key. The encryption program encrypts [UID,pPKU]_(mSKU) using the public key of the certificate authority and sends PKC([UID,pPKU]_(mSKU)) to the certificate authority via a communications path as a request for a certified pseudonym public key (i.e., a request for the issuance of a license).

The certificate authority receives the request (PKC([UID,pPKU]_(mSKU))) and the decryption program decrypts request using the secret key SKC of the certificate authority. The signature verifying program verifies the validity of the user signature using the user's master public key mPKU. If the signature is valid, the certificate authority signature generating program generates a signature (license) [pPKU]_(SKC) for the user's pseudonym public key using the certificate authority's secret key SKC, and stores the user's pseudonym public key in the storage device in connection with the user's master public key mPKU and the user's real identification UID. The certificate authority encryption program encrypts the license [pPKU]_(SKC) using the user's master public key mPKU and sends the license mPKU([pPKU]_(SKC)) to the user via a communications path.

The user receives the encrypted license mPKU([pPKU]_(SKC)) and the decryption program decrypts the license using the user's master secret key mSKU. The signature verifying program verifies the validity of the license [pPKU]_(SKC) using the public key PKC of the certificate authority. If the license is valid, the license is stored in the storage device.

Referring to FIG. 4, the user encryption program encrypts the license [pPKU]_(SKC), pseudonym public key pPKU using the public key PKI of the digital cash issuer and sends the encrypted license PKI([pPKU]_(SKC),pPKU) to the digital cash issuer via a communications path as a request for registration in the digital cash issuer and for the digital cash issuer license.

The digital cash issuer receives the request PKI([pPKU]_(SKC),pPKU) and the decryption program decrypts the information using the secret key SKI of the digital cash issuer. The digital cash issuer searches for pPKU in its storage to prevent the use of another user's pseudonym public key. If the user's pseudonym public key pPKU is not registered, the digital cash issuer signature verifying program verifies the validity of the license [pPKU]_(SKC) the using the certificate authority's public key PKC. If the license is valid, the digital cash issuer assigns a storage space to the user and stores the user's pseudonym public key pPKU. The digital cash issuer signature generating program signs the user's pseudonym public key pPKU the using the secret key of the digital cash issuer SKI. The encryption program encrypts the information using the user's pseudonym public key pPKU and sends pPKU([pPKU]_(SKI)) as a license to the user via a communications path.

The user receives pPKU([pPKU]_(SKI)), and the decryption program decrypts the license using the user's pseudonym secret key pSKU. The signature verifying program verifies the validity of the digital cash issuer signature using the digital cash issuer's public key PKI. If the signature is valid, the license [pPKU]_(SKI) is stored in the storage device. The user may obtain additional certified pseudonym public keys without a limit.

(2) Withdrawal Procedure (I.E., the Electronic Cash Issuing Procedure)

FIGS. 5-8 show a diagrammatic representation of the withdrawal protocol. Referring to FIGS. 5 and 6, the user signature generating program signs the user's pseudonym public key pPKU and the amount of digital cash x using the user's pseudonym secret key pSKU. The encryption program encrypts the signed user's pseudonym public key and the amount of digital cash [pPKU,x]_(pSKU) using the digital cash issuer's public key PKI. The signature generating program signs the user real identification UID, the amount of money to be withdrawn x, the encrypted signed user's pseudonym public key, and the amount of digital cash PKI([pPKU,x]_(pSKU)) using the user's master secret key mSKU. The encryption program encrypts the information using the public key of the bank PKB and sends PKB([PKI([pPKU,x]_(pSKU)),UID,x]_(mSKU)) to the user's bank via a communications path.

The bank decryption program decrypts PKB([PKI([pPKU,x]_(pSKU)),UID,x]_(mSKU)) using the bank's secret key SKB and the signature verifying program verifies the validity of the signature for authentication with the master public key of the user mPKU. If the signature is valid, the amount of money x is withdrawn from the user account. The signature generating program signs the encrypted signed user's pseudonym public key, the amount of digital cash PKI([pPKU,x]_(pSKU), and the withdrawn amount of money x using the bank's secret key SKB. The encryption program encrypts the information using the public key of the digital cash issuer PKI and sends the information PKI([PKI([pPKU,x]_(pSKU)),x]_(SKB)) to the digital cash issuer via a communications path.

Referring to FIG. 7, the digital cash issuer receives the information PKI([PKI([pPKU,x]_(pSKU)),x]_(SKB)), and the decryption program decrypts the information using the digital cash issuer's secret key SKI. The signature verifying program verifies the signature of the bank using the public key of the user's bank PKB. If the signature is valid, the digital cash issuer decryption program decrypts PKI([pPKU,x]_(pSKU)) using the digital cash issuer's secret key. The signature verifying program verifies the signature of the user using the user's pseudonym public key pPKU to authenticate the user. If the signature is valid, the issuer verifies the equality of the two amounts x. The amounts are not equal, the real identity of the user is revealed by sending pPKU to the certificate authority. If the amounts are equal, the digital cash issuer issues a digital cash token that includes the following information: (i) digital cash amount, and (ii) random number. The digital cash issuer generates a random number Rd and stores the random number in the storage device. The signature generating program signs the digital cash amount x and random number Rd using the digital cash issuer's secret key SKI. The encryption program encrypts the digital cash token using the user's pseudonym public key pPKU. The signature generating program signs the encrypted digital cash token pPKU([x,Rd]SKI) using the digital cash issuer's secret key SKI. The encryption program encrypts the information [pPKU([x,Rd]SKI)]SKI using the public key of the bank PKB, and sends encrypted information PKB([pPKU([x,Rd]SKI)]SKI) to the user's bank via a communications path.

Referring to FIG. 8, the user's bank receives the information PKB([pPKU([x,Rd]SKI)]SKI) and the decryption program decrypts the information using the user's bank secret key SKB. The signature verifying program verifies the digital cash issuer signature using the public key of the digital cash issuer PKI. If the signature is valid, the encrypted digital cash token pPKU([x,Rd]SKI) is sent to the user via a communications path.

The user receives the encrypted digital cash token pPKU([x,Rd]SKI). The decryption program decrypts the digital cash token using the user's pseudonym secret key. The signature verifying program verifies the validity of the digital cash issuer signature using the digital cash issuer's public key PKI. If the signature is valid, the digital cash token [x,Rd]SKI is stored in the storage device of the user. The user can easily transfer the issued digital cash token to another user who has a certified pseudonym public key.

(3) Payment Procedure

FIGS. 9-12 show the diagrammatic representation of the payment protocol. Referring to FIGS. 9 and 10, the user encryption program encrypts the digital cash token [x,Rd]SKI and the digital cash issuer license [pPKU]SKI using the public key of the shop PKS, and sends the encrypted information to the shop as request for payment. The user can send a payment request using another certified pseudonym public key, because the pseudonym is not associated with digital cash token. As a result, the pseudonym may be changed at the time of payment thereby increasing user flexibility.

The shop decryption program decrypts the encrypted digital cash token and the digital cash issuer license PKS([x,Rd]SKI, [pPKU]SKI) using the shop's secret key SKS. The signature verifying program verifies the signature of the issuer using the digital cash issuer public key PKI. If the signatures are valid, the shop stores the user's digital cash issuer license and the digital cash token. The random number generating program generates a random number Rs, and the time generating program generates a time Ts. The encryption program encrypts Rs, Ts, and the shop identification SID using the user's pseudonym public key pPKU, and sends the encrypted information pPKU(Rs,Ts,SID) to the user via a communications path.

The user receives the encrypted information pPKU(Rs,Ts,SID). The decryption program decrypts the information using the user's pseudonym secret key pSKU. The signature generating program signs the random number Rs, the time Ts, and the shop identification SID using the user's pseudonym secret key pSKU. The encryption program encrypts the information using the public key of the shop PKS, and sends the encrypted information PKS([Rs,Ts,SID]pSKU) to the shop via a communications path.

The shop receives the information PKS([Rs,Ts,SID]pSKU), and the decryption program decrypts the information using the shop's secret key SKS. The signature verifying program verifies the signature using the user's pseudonym public key pPKU. If the signature is valid, the shop stores the challenge and regards the payment as valid.

Referring to FIG. 11, after a period of time, the shop encryption program encrypts the information including the challenge that was signed by the user [Rs,Ts,SID]pSKU, the digital cash token [x,Rd]SKI, and the user's digital cash issuer license [pPKU]SKI, using the public key of the digital cash issuer PKI, and sends the information to the digital cash issuer via a communications path.

The digital cash issuer decryption program decrypts PKI([Rs,Ts,SID]pSKU, [x,Rd]SKI, [pPKU]SKI) using the digital cash issuer's secret key SKI. The signature verifying program verifies the signatures using the digital cash issuer's public key PKI and the user's pseudonym public key pPKU. If the signatures are valid, the issuer checks the random number Rd. If the random number Rd does not exist, it is determined that there is a double spending, and the real identity is revealed by sending the user's pseudonym public key pPKU to the certificate authority. If Rd exists, the random number is deleted, and the digital cash issuer stores the challenge [Rs,Ts,SID]pSKU in the storage device.

Referring to FIG. 12, the digital cash issuer signature generating program signs the shop identification SID and the amount x to be deposited for the shop with the digital cash issuer's secret key SKI. The encryption program encrypts the information using the public key of the shop's bank PKB, and sends the information PKB([SID,x]SKI) to the shop's bank via a communications path.

The shop's bank receives PKB([SID,x]_(SKI)) and the decryption program decrypts the information using the secret key SKB. The signature verifying program verifies the signature with the public key of the issuer PKI. If the signature is valid, the shop's bank adds the amount of money x to the shop's account.

Second Embodiment

In another example, against that because issued public keys may be passed outside of the issuer's control, a more powerful encryption may be used to protect against any public key leakage and misuse. A cryptographic coprocessor is used such that once data is encrypted, the data may not be decrypted without use of the coprocessor. In this example, the certification authority, use, and bank entities are as described above, however, the certificate issuer also is provided with a cryptographic coprocessor.

(1) User Registration Procedure

The user registration procedure for this example is the same as described above for FIGS. 2-4.

(2) Withdrawal Procedure (I.E., Electronic Cash Issuing Procedure)

FIGS. 13-16 show the diagrammatic representation of a withdrawal protocol. Referring to FIGS. 13 and 14, the user signature generating program signs the user's pseudonym public key pPKU and the amount of digital cash x using the user's pseudonym secret key pSKU. The encryption program encrypts the signed user's pseudonym public key and the amount of digital cash [pPKU,x]_(pSKU) using the public key of a cryptographic coprocessor PKP. The signature generating program signs the user real identification UID, the amount of money to be withdrawn x, and PKP([pPKU,x]_(pSKU)) using the user's master secret key mSKU. The encryption program encrypts the information using the public key of the user's bank PKB and sends the information PKB([PKP([pPKU,x]_(pSKU)),UID,x]_(mSKU)) to the user's bank via a communications path.

The user's bank decryption program decrypts the information PKB([PKP([pPKU,x]_(pSKU)),UID,x]_(mSKU)) using the bank's secret key. The signature verifying program verifies the validity of the signature for authentication with the master public key of the user mPKU. If the signature is valid, the amount of money x is withdrawn from the user account. The signature generating program signs the amount x that is withdrawn from the user account using the user's bank's secret key SKB and the encryption program encrypts [x]_(SKB) using the public key of the cryptographic coprocessor PKP. The information PKP([pPKU,x]_(pSKU)) and PKP([x]_(SKB)) is sent to the digital cash issuer via a communications path.

Referring to FIG. 15, the digital cash issuer receives PKP([pPKU,x]_(pSKU)) and PKP([x]_(SKB)), and decrypts the information using the secret key of the cryptographic coprocessor to obtain the signed user's pseudonym public key, the amount of digital cash [pPKU,x]_(pSKU) and the signed amount of withdrawn money from the user account [x]_(SKB). The signature verifying program verifies the signature of the bank using the public key of the bank PKB. If the signature is valid, the digital cash issuer signature verifying program verifies the user's signature [pPKU,x]_(pSKU) using the user's pseudonym public key pPKU. If the user's signature is valid, the issuer verifies that the two amounts x are equal. If the amounts are not equal, the real identity of the user is revealed by sending pPKU to the certificate authority. If the amounts are equal, the digital cash issuer issues a digital cash token which includes the information: (i) digital cash amount, and (ii) random number. The digital cash issuer generates a random number Rd and stores it in the storage device. The signature generating program signs digital cash amount x and random number Rd using the digital cash issuer's secret key SKI. The encryption program encrypts the information using user's pseudonym public key pPKU, and the signature generating program signs the encrypted information pPKU([x,Rd]SKI) using the digital cash issuer's secret key SKI. The encryption program encrypts [pPKU([x,Rd]SKI)]SKI using the public key of the bank PKB, and sends the information PKB([pPKU([x,Rd]SKI)]SKI) to the user's bank via a communications path.

Referring to FIG. 16, the user's bank receives the information PKB([pPKU([x,Rd]SKI)]SKI), and the decryption program decrypts the information using the user's bank secret key SKB. The signature verifying program verifies the digital cash issuer signature using the public key of the digital cash issuer PKI. If the signature is valid, the bank sends the encrypted digital cash token pPKU([x,Rd]SKI) to the user via a communications path.

The user receives the encrypted digital cash token pPKU([x,Rd]SKI), and the decryption program decrypts the information using the user's pseudonym secret key pSKU. The signature verifying program verifies the validity of the digital cash issuer signature with the digital cash issuer's public key PKI. If the signature is valid, the digital cash token [x,Rd]SKI is stored in the storage device of the user. Using this embodiment, the user can easily transfer the issued digital cash token to another user who has a certified pseudonym public key.

(3) Payment Procedure

The payment procedure is the same as that described above for FIGS. 9-12.

Third Embodiment

In the previous embodiments, the withdrawal process and the payment process are performed from fixed positions, which require the user to access user station to buy or to get digital cash. For more convenience and accessibility, the following example allows a user to use a mobile device to buy and to get digital cash. The user mobile device in this implementation includes a processing device, a storage device, an encryption program, and a decryption program. However, because the storage and the computational power of most conventional mobile devices are limited, the mobile device implementation may provide only a minimum requirement to protect the security and privacy.

(1) User Registration Procedure

The user registration procedure for this example is the same as described above for FIGS. 2, 3, and 4.

(2) Withdrawal Procedure (Electronic Cash Issuing Procedure)

FIGS. 17-22 show a diagrammatic representation of the withdrawal protocol. Referring to FIGS. 17 and 18, the user's mobile device encryption program encrypts the user's pseudonym public key pPKU and the amount of digital cash x using a mobile—home based shared secret key MHS. The mobile device sends the information MHS(pPKU,x) to the user's station via a communications path.

The user's station receives the encrypted user's pseudonym public key and the amount of digital cash MHS(pPKU,x) and the decryption program decrypts the information using the mobile/home shared secret key MHS. The home base station determines if the decrypted pseudonym public key matches the user's pseudonym public key. If they are the same, the user's mobile device is authenticated by the user's home station.

Referring to FIG. 19, the user's home station signature generating program signs the user's pseudonym public key pPKU and the amount of digital cash x using the user's pseudonym secret key pSKU. The encryption program encrypts the signed user's pseudonym public key and the amount of digital cash [pPKU,x]_(pSKU) using the public key of a cryptographic coprocessor PKP. The signature generating program signs the user real identification UID, the amount of money to be withdrawn x, and PKP([pPKU,x]_(pSKU)) using the user's master secret key mSKU. The encryption program encrypts the information using the public key of the user's bank PKB and sends PKB([PKP([pPKU,x]_(pSKU)),UID,x]_(mSKU)) to the user's bank via a communications path.

The user's bank decryption program decrypts PKB([PKP([pPKU,x]_(pSKU)),UID,x]_(mSKU)) using the user's bank's secret key. The signature verifying program verifies the validity of the signature for authentication with the master public key of the user mPKU. If the signature is valid, the amount of money x is withdrawn from the user account. The signature generating program signs the amount x that is withdrawn from the user account using the user's bank's secret key SKB. The encryption program encrypts [x]_(SKB) using the public key of the cryptographic coprocessor PKP, and sends information PKP([pPKU,x]_(pSKU)) and PKP([x]_(SKB)) to the digital cash issuer via a communications path.

Referring to FIG. 20, the digital cash issuer receives PKP([pPKU,x]_(pSKU)) and PKP([x]_(SKB)), and decrypts the information using the secret key of the cryptographic coprocessor to obtain the signed user's pseudonym public key, the amount of digital cash [pPKU,x]_(pSKU), and the signed amount of withdrawn money from the user account [x]_(SKB). The signature verifying program verifies the signature of the user's bank using the public key of the bank PKB. If the signature is valid, the digital cash issuer signature verifying program verifies the user's signature [pPKU,x]_(pSKU) using the user's pseudonym public key pPKU. If the signature is valid, the issuer verifies that the two amounts x are equal. If the amounts are not equal, the real identity of the user is revealed by sending pPKU to the certificate authority via a communications path. If the amounts are equal, the digital cash issuer issues a digital cash token that includes the information: (i) digital cash amount, and (ii) random number. The digital cash issuer generates a random number Rd and stores the Rd in the storage device. The signature generating program signs the digital cash amount x and random number Rd using the digital cash issuer's secret key SKI. The encryption program encrypts the digital cash token using user's pseudonym public key pPKU. The signature generating program signs the encrypted digital cash token pPKU([x,Rd]SKI) using the digital cash issuer's secret key SKI. The encryption program encrypts the information [pPKU([x,Rd]SKI)]SKI using the public key of the bank PKB, and sends the information PKB([pPKU([x,Rd]SKI)]SKI) to the user's bank via a communications path.

Referring to FIG. 21, the user's bank receives the information PKB([pPKU([x,Rd]SKI)]SKI). The decryption program decrypts the information using the user's bank secret key SKB. The signature verifying program verifies the digital cash issuer signature using the public key of the digital cash issuer PKI. If the signature is valid, the encrypted digital cash token pPKU([x,Rd]SKI) is sent to the user's home station via a communications path.

The user's home station receives the information pPKU([x,Rd]SKI). The decryption program decrypts the information using the user's pseudonym secret key pSKU. The signature verifying program verifies the validity of the digital cash issuer signature with the digital cash issuer's public key PKI. If the signature is valid, the digital cash token [x,Rd]SKI is stored in the storage device of the user's home station.

Referring to FIG. 22, the user's home station encryption program encrypts the value of the digital cash token x and the user's pseudonym public key pPKU using the mobile/home shared secret key MHS, and sends the encrypted value MHS(pPKU,x) to the user's mobile device via a communications path.

The user's mobile device receives the encrypted value of the digital cash token and the user's pseudonym public key MHS(pPKU,x). The decryption program decrypts the information using the mobile/home shared secret key MHS. The mobile device determines if the user's pseudonym public key matches the decrypted user pseudonym public key to authenticate the user's home station. If the keys match, the user stores the value of digital cash token in the storage of the mobile device's. According to this embodiment, the user can easily transfer the issued digital cash token to another user who has certified pseudonym public key.

(3) Payment Procedure

FIGS. 23-27 show the diagrammatic representation of the payment protocol. Referring to FIGS. 23 and 24, the user's mobile device chooses the value of the digital cash token x and the encryption program encrypts the value and the user's pseudonym public key pPKU using the mobile/home shared secret key MHS and sends the encrypted information MHS(pPKU,x) to the user's station via a communications path.

The user's home station receives the encrypted information MHS(pPKU,x) and the decryption program decrypts the information using the mobile/home shared secret key MHS and uses the decrypted to authenticate the user's mobile device. If the decrypted user's pseudonym public key matches the user's pseudonym public key, the user's home station finds the digital cash token that is equivalent to the value that was sent by the user's mobile device.

Referring to FIG. 25, the user's home station encryption program encrypts the digital cash token [x,Rd]SKI and the digital cash issuer license [pPKU]SKI using the public key of the shop PKS, and sends the encrypted information to the shop as request for payment. The user's home station may send a payment request using another certified pseudonym public key. As a result, the user may change the pseudonym at the payment time because the pseudonym is not associated with digital cash token, giving the user flexibility in their payment options.

The shop decryption program decrypts the encrypted digital cash token and the digital cash issuer license PKS([x,Rd]SKI, [pPKU]SKI) using the shop's secret key SKS. The signature verifying program verifies the signature of the issuer with the digital cash issuer public key PKI. If the signatures are valid, the shop stores the user's digital cash issuer license and the digital cash token. The shop random number generating program generates a random number Rs, and the time generating program generates the time Ts. The encryption program encrypt Rs, Ts, and the shop identification SID using the user's pseudonym public key pPKU, and sends the encrypted information pPKU(Rs,Ts,SID) to the user's home station via a communications path.

The user's home station receives the encrypted information pPKU(Rs,Ts,SID). The decryption program decrypts the information using the user's pseudonym secret key pSKU. The signature generating program signs the random number Rs, the time Ts, and the shop identification SID using the user's pseudonym secret key pSKU. The encryption program encrypts the information using the public key of the shop PKS, and sends the encrypted information PKS([Rs,Ts,SID]pSKU) to the shop via a communications path.

The shop receives the encrypted information PKS([Rs,Ts,SID]pSKU). The decryption program decrypts the information using the shop's secret key SKS. The signature verifying program verifies the signature using the user's pseudonym public key pPKU. If the signature is valid, the shop stores the challenge and the shop regards the payment as valid.

Referring to FIG. 26, after a period of time the shop encryption program encrypts the information that includes the challenge that was signed by the user [Rs,Ts,SID]pSKU, the digital cash token [x,Rd]SKI, and the user's digital cash issuer license [pPKU]SKI, using the public key of the digital cash issuer PKI, and sends the information to the digital cash issuer via a communications path.

The digital cash issuer decryption program decrypts PKI([Rs,Ts,SID]pSKU, [x,Rd]SKI, [pPKU]SKI) using the digital cash issuer's secret key SKI. The signature verifying program verifies the signatures using the digital cash issuer's public key PKI and the user's pseudonym public key pPKU. If the signatures are valid, the issuer checks the random number Rd. If the random number Rd does not exist, it is determined that there has been a double spending and the real identity is revealed by sending the user's pseudonym public key pPKU to the certificate authority. If the random number Rd exists, the random number is deleted, and the digital cash issuer stores the challenge [Rs,Ts,SID]pSKU in its storage device.

Referring to FIG. 27, the digital cash issuer signature generating program signs the shop identification SID, and the amount x to be deposited for the shop with the digital cash issuer's secret key SKI. The encryption program encrypts the information using the public key of the shop's bank PKB and sends PKB([SID,x]_(SKI)) to the shop's bank via a communications path.

The shop's bank receives PKB([SID,x]_(SKI)) and the decryption program decrypts the information using the secret key SKB. The signature verifying program verifies the signature with the public key of the issuer PKI. If the signature is valid, the shop's bank adds the amount of money x to the shop's account.

Fourth Embodiment

In the previous embodiments described above public key encryption is used. Public key encryption adds a cost in power and time used to complete a transaction. Therefore, a shared secret key may be used in place of the public key to hide the pseudonym and the amount of the digital cash as described in the following example. In this example, the certificate authority, bank, and user are as described above; however, in addition to the elements described above, the issuer further includes a key pointer KPr generating program.

(1) User Registration Procedure

FIGS. 28-30 show the diagrammatic representation of the registration protocol. Referring to FIGS. 28 and 29, the user the key generating program generates a pseudonym public key and a pseudonym secret key. The signature generating program signs the pseudonym public key and the user real identification using user's master secret key. The encryption program encrypts [UID,pPKU]_(mSKU) using the public key of the certificate authority and sends PKC([UID,pPKU]_(mSKU)) to the certificate authority as a request for a certified pseudonym public key (i.e., a request for the issuance of a license).

The certificate authority receives the request (PKC([UID,pPKU]_(mSKU))) and the decryption program decrypts the request using the secret key of the certificate authority SKC. The signature verifying program verifies the validity of the user signature using the user's master public key mPKU. If the signature is valid, the certificate authority the signature generating program generates a signature (i.e., a license) [pPKU]_(SKC) for the user's pseudonym public key using the certificate authority's secret key SKC, and stores the user's pseudonym public key in the storage device in connection with the user's master public key mPKU and the user's real identification UID. The certificate authority encryption program encrypts the license [pPKU]_(SKC) using the user's master public key mPKU and sends mPKU([pPKU]_(SKC)) to the user via a communications path.

The user receives the encrypted license mPKU([pPKU]_(SKC)) and the decryption program decrypts the license using the user's master secret key mSKU. The signature verifying program verifies the validity of the license [pPKU]_(SKC) using the public key of the certificate authority PKC. If the signature is valid, the user key generating program establishes a user-issuer shared secret key S and stores the license and the user-issuer shared secret key in the user storage device.

Referring to FIG. 30, the user encryption program encrypts the license [pPKU]_(SKC), pseudonym public key pPKU, and the user-issuer shared secret key S using the public key of the digital cash issuer PKI. The user then sends PKI([pPKU]_(SKC),pPKU,S) to the digital cash issuer via a communications path.

The digital cash issuer receives PKI([pPKU]_(SKC),pPKU,S) and the decryption program decrypts the information using the secret key of the digital cash issuer SKI. The digital cash issuer searches for pPKU in its storage device to prevent misuse of other users' pseudonym public key. If the user's pseudonym public key pPKU is not already registered, the digital cash issuer signature verifying program verifies the validity of the license [pPKU]_(SKC) using the certificate authority's public key PKC. If the license valid, the digital cash issuer assigns an empty storage space to the user and generates a key pointer KPr to identify the user-issuer shared secret key S. In addition, the cash issuer also stores the user's pseudonym public key pPKU, the user-issuer shared secret key S and the key pointer KPr in the storage device. The digital cash issuer signature generating program signs the user's pseudonym public key pPKU and the key pointer KPr using the secret key of the issuer SKI. The encryption program encrypts the information using the user-issuer shared secret key S and sends S([pPKU, KPr]_(SKI)) as an acknowledgment to the user via a communications path.

The user receives the acknowledgement S([pPKU, KPr]_(SKI)), and the decryption program decrypts the information using the user-issuer shared secret key S. The signature verifying program verifies the validity of the digital cash issuer signature using the digital cash issuer's public key PKI. If the signature valid, the digital cash issuer stores the license [pPKU]_(SKI) and the key pointer KPr in the storage device. According to this example, the user may obtain an unlimited number of certified pseudonym public keys.

(2) Withdrawal Procedure (Electronic Cash Issuing Procedure)

FIGS. 31-34 show the diagrammatic representation of the withdrawal protocol. Referring to FIGS. 31 and 32, the user encryption program encrypts the user's pseudonym public key pPKU and the amount of digital cash x using the user-issuer shared secret key S. The signature generating program signs the user real identification UID, the amount of money to be withdrawn x, the encrypted user's pseudonym public key, the amount of digital cash S(pPKU,x), and the key pointer KPr using the user's master secret key mSKU. The encryption program encrypts the information using the public key of the user's bank PKB and sends PKB([S(pPKU,x),UID,x,KPr]_(SKU)) to the user's bank via a communications path.

The user's bank decryption program decrypts PKB([S(pPKU,x),UID,x,KPr]_(mSKU)) using the user's bank's secret key. The signature verifying program verifies the validity of the signature for authentication with the master public key of the user mPKU. If the signature is valid, the amount of money x is withdrawn from the user account, and the signature generating program signs the encrypted user's pseudonym public key, the amount of digital cash S(pPKU,x), the key pointer KPr, and the withdrawn amount of money x using the bank's secret key SKB. The encryption program encrypts the information using the public key of the digital cash issuer PKI and sends PKI([S(pPKU,x),KPr,x]_(SKB)) to the digital cash issuer via a communications path.

Referring to FIG. 33, the digital cash issuer receives PKI([S(pPKU,x),KPr,x]_(SKB)), and the decryption program decrypts the information using the digital cash issuer's secret key SKI. The signature verifying program verifies the signature of the bank using the public key of the user's bank PKB. If the signature is valid, the digital cash issuer uses the key pointer KPr to search for the user-issuer shared secret key S. Once found the decryption program decrypts S(pPKU,x) using the user-issuer shared secret key S to authenticate the user by matching the user's pseudonym public key after the decryption. If the decrypted key matches the user's pseudonym key, the use is authenticated. The issuer verifies that the two amounts x are equal. If the amounts are not equal, the real identity of the user is revealed by sending pPKU to the certificate authority. If the amounts are equal, the digital cash issuer issues a digital cash token that includes the following information: (i) digital cash amount, and (ii) random number. The digital cash issuer generates the random number Rd and stores the number in its storage device. The signature generating program signs the digital cash amount x and random number Rd using the digital cash issuer's secret key SKI. The encryption program encrypts the information using the user-issuer shared secret key S. The signature generating program signs the encrypted information S([x,Rd]SKI) using the digital cash issuer's secret key SKI. The encryption program encrypts [S([x,Rd]SKI)]SKI using the public key of the user's bank PKB, and sends PKB([S([x,Rd]SKI)]SKI) to the user's bank via a communications path.

Referring to FIG. 34, the user's bank receives the information PKB([S([x,Rd]SKI)]SKI), and the decryption program decrypts the information using the user's bank secret key SKB. The signature verifying program verifies the digital cash issuer signature using the public key of the digital cash issuer PKI. If the signature is valid, the bank sends the encrypted digital cash token S([x,Rd]SKI) to the user via a communications path.

The user receives the encrypted digital cash token S([x,Rd]SKI). The decryption program decrypts the digital cash token using the user-issuer shared secret key S. The signature verifying program verifies the validity of the digital cash issuer signature with the digital cash issuer's public key PKI. If the signature is valid, the digital cash token S([x,Rd]SKI) is stored in the storage device of the user. According to this embodiment, the user can easily transfer the issued digital cash token to another user who has certified pseudonym public key.

(3) Payment Procedure

The payment procedure is the same as that described above for FIGS. 9-12.

Fifth Embodiment

The previous embodiment employs a common key pointer between the digital cash issuer and the bank to provide an means to link the user's real identification and the user's pseudonym public key. In the following example, the digital cash issuer may use a cryptographic coprocessor to provide stronger protection of the user's privacy. In this implementation, the user encrypts the key pointer using the public key of cryptographic coprocessor. As a result, the bank may not obtain any data shared between the user's real identification and the user's pseudonym public key. In addition, the cryptographic coprocessor provides stronger encryption such that whenever the data is encrypted, the date may not be decrypted without the coprocessor.

(1) User Registration Procedure

The user registration procedure for this example is the same as described above for FIGS. 2, 3, and 4.

(2) Withdrawal Procedure (Electronic Cash Issuing Procedure)

FIGS. 35-38 show the diagrammatic representation of the withdrawal protocol. Referring to FIGS. 35 and 36, the user encryption program encrypts the user's pseudonym public key pPKU and the amount of digital cash x using the user-issuer shared secret key S. The encryption program encrypts the encrypted user's pseudonym public key, the amount of digital cash S(pPKU,x), and the key pointer KPr using the public key of a cryptographic coprocessor PKP. The signature generating program signs the user real identification UID, the amount of money to be withdrawn x, and PKP(S(pPKU,x),KPr) using the user's master secret key mSKU. The encryption program encrypts the information using the public key of the user's bank PKB and sends PKB([PKP(S(pPKU,x),KPr),UID,x]_(mSKU)) to the user's bank via a communications path.

The user's bank decryption program decrypts PKB([PKP(S(pPKU,x),KPr),UID,x]_(mSKU)) using the user's bank's secret key. The signature verifying program verifies the validity of the signature for authentication with the master public key of the user mPKU. If the signature is valid, the amount of money x is withdrawn from the user account. The signature generating program signs the amount x that is withdrawn from the user account by using the user's bank's secret key SKB. The encryption program encrypts [x]_(SKB) using the public key of the cryptographic coprocessor PKP, and sends information PKP(S(pPKU,x),KPr) and PKP([x]_(SKB)) to the digital cash issuer via a communications path.

Referring to FIG. 37, the digital cash issuer receives PKP(S(pPKU,x),KPr) and PKP([x]_(SKB)), and decrypts the information using the secret key of the cryptographic coprocessor to obtain the encrypted user's pseudonym public key, the amount of digital cash S(pPKU,x), the key pointer KPr, and the signed amount of withdrawn money from the user account [x]_(SKB). The signature verifying program verifies the signature of the bank using the public key of the user's bank PKB. If the signature is valid, the digital cash issuer searches for the user-issuer shared secret key S using the key pointer KPr. Once s is obtained, the decryption program decrypts S(pPKU,x) using the user-issuer shared secret key S to authenticate the user by matching decrypted key with the user's pseudonym public key. If the keys match, the user is authenticated, and the issuer verifies that the two amounts x are equal. If the amounts are not equal, the real identity of the user is revealed by sending pPKU to the certificate authority. If the amounts are equal, the digital cash issuer issues a digital cash token that includes the following information: (i) digital cash amount, and (ii) random number. The digital cash issuer generates random a number Rd and stores the random number in its storage device. The digital cash issuer signature generating program signs the digital cash amount x and the random number Rd using the digital cash issuer's secret key SKI. The encryption program encrypts the information using the user-issuer shared secret key S. The signature generating program signs the encrypted information S([x,Rd]SKI) using the digital cash issuer's secret key SKI. The encryption program encrypts the signed information [S([x,Rd]SKI)]SKI using the public key of the user's bank PKB, and sends the encrypted information PKB([S([x,Rd]SKI)]SKI) to the user's bank via a communications path.

Referring to FIG. 38, the user's bank receives the encrypted information PKB([S([x,Rd]SKI)]SKI), and the decryption program decrypts the information using the user's bank secret key SKB. The signature verifying program verifies the digital cash issuer signature using the public key of the digital cash issuer PKI. If the signature is valid, the issuer sends the encrypted digital cash token S([x,Rd]SKI) to the user via a communications path.

The user receives the encrypted digital cash token S([x,Rd]SKI), and the decryption program decrypts the information using the user-issuer shared secret key S. The signature verifying program verifies the validity of the digital cash issuer signature with the digital cash issuer's public key PKI. If the signature is valid, the digital cash token [x,Rd]SKI is stored in the storage device of the user. According to this embodiment, the user can easily transfer the issued digital cash token to another user who has certified pseudonym public key.

(3) Payment Procedure

The payment procedure is the same as that described above for FIGS. 9-12.

Sixth Embodiment

The following example provides the enhanced privacy and encryption of the previous example described above, in a mobile user device environment.

(1) User Registration Procedure

The user registration procedure is the same as that described above for FIGS. 28-30.

(2) Withdrawal Procedure (I.E., Electronic Cash Issuing Procedure)

FIGS. 39-44 show the diagrammatic representation of the withdrawal protocol. Referring to FIGS. 39 and 40, the user's mobile device encryption program encrypts the user's pseudonym public key pPKU and the amount of digital cash x using the mobile/home shared secret key MHS and sends the information MHS(pPKU,x) to the user station via a communications path.

The user station receives the encrypted user's pseudonym public key and the amount of digital cash MHS(pPKU,x), and the decryption program decrypts the information using the mobile/home shared secret key MHS. The user station determines if the decrypted key matches the user's pseudonym public key. If the keys match, the user's mobile device is authenticated by the user station.

Referring to FIG. 41, the user station encryption program encrypts the user's pseudonym public key pPKU and the amount of digital cash x using the user-issuer shared secret key S. The encryption program encrypts the encrypted user's pseudonym public key, the amount of digital cash S(pPKU,x), and the key pointer KPr using the public key of a cryptographic coprocessor PKP. The signature generating program signs the user real identification UID, the amount of money to be withdrawn x, and PKP(S(pPKU,x),KPr) using the user's master secret key mSKU. The encryption program encrypts the information using the public key of the user's bank PKB and sends PKB([PKP(S(pPKU,x),KPr),UID,x]_(mSKU)) to the user's bank via a communications path.

The user's bank decryption program decrypts PKB([PKP(S(pPKU,x),KPr),UID,x]_(mSKU)) by using the user's bank's secret key. The signature verifying program verifies the validity of the signature for authentication with the master public key of the user mPKU. If the signature is valid, he amount of money x is withdrawn from the user account, and the signature generating program signs the amount x that is withdrawn from the user account using the user's bank's secret key SKB. The encryption program encrypts [x]_(SKB) using the public key of the cryptographic coprocessor PKP, and sends information PKP(S(pPKU,x),KPr) and PKP([x]_(SKB)) to the digital cash issuer via a communications path.

Referring to FIG. 42, the digital cash issuer receives PKP(S(pPKU,x),KPr) and PKP([x]_(SKB)), and decrypts the information using the secret key of the cryptographic coprocessor to obtain the encrypted user's pseudonym public key, the amount of digital cash S(pPKU,x), the key pointer KPr, and the signed amount of withdrawn money from the user account [x]_(SKB). The signature verifying program verifies the signature of the user's bank by using the public key of the bank PKB. If the signature is valid, the digital cash issuer searches for the user-issuer shared secret key S using the key pointer KPr. Once found, the decryption program decrypts S(pPKU,x) using the user-issuer shared secret key S to authenticate the user by matching the decrypted key with the user's pseudonym public key. If the keys match, the user is authenticated, and the issuer verifies that the two amounts x are equal. If the amounts are not equal, the real identity of the user is revealed by sending pPKU to the certificate authority. If the amounts are equal, the digital cash issuer issues digital cash token that includes the following information: (i) digital cash amount, and (ii) random number. The digital cash issuer generates a random number Rd and stores it in its storage device. The signature generating program signs the digital cash amount x and the random number Rd using the digital cash issuer's secret key SKI. The encryption program encrypts the information using the user-issuer shared secret key S. The signature generating program signs the encrypted information S([x,Rd]SKI) using the digital cash issuer's secret key SKI. The encryption program encrypts the signed information [S([x,Rd]SKI)]SKI using the public key of the user's bank PKBm, and sends the encrypted information PKB([S([x,Rd]SKI)]SKI) to the user's bank via a communications path.

Referring to FIG. 43, the user's bank then receives the information PKB([S([x,Rd]SKI)]SKI) and the decryption program decrypts the information using the user's bank secret key SKB. The signature verifying program verifies the digital cash issuer signature using the public key of the digital cash issuer PKI. If the signature is valid, the issuer sends the encrypted digital cash token S([x,Rd]SKI) to the user's home station via a communications path.

The user's home station receives the encrypted digital cash token S([x,Rd]SKI), and the decryption program decrypts the information using the user-issuer shared secret key S. The signature verifying program verifies the validity of the digital cash issuer signature using the digital cash issuer's public key PKI. If the signature is valid, the digital cash token [x,Rd]SKI is stored in the storage device of the user's home station.

Referring to FIG. 44, the user's home station encryption program encrypts the value of the digital cash token x and the user's pseudonym public key pPKU using the mobile/home shared secret key MHS, and sends the encrypted information MHS(pPKU,x) to the user's mobile device via a communications path.

The user's mobile device receives the encrypted value of the digital cash token and the user's pseudonym public key MHS(pPKU,x), and the decryption program decrypts the information using the mobile/home shared secret key MHS. The mobile device determines if the user's pseudonym public key matches the decrypted user pseudonym public key to authenticate the user's home base station. If they match, the user stores the value of digital cash token in the mobile device's storage device. Using this embodiment, the user can easily transfer the issued digital cash token to another user who has certified pseudonym public key.

(3) Payment Procedure

The payment protocol is the same as that described above for FIGS. 23 and 24-27.

Seventh Embodiment

The previous embodiments described above are implemented as off-line protocols. However, these protocols may be modified for on-line operation. One possible example follows.

(1) User Registration Procedure

The user registration protocol is the same as described above for FIGS. 2, 3, and 4.

(2) Withdrawal Procedure (Electronic Cash Issuing Procedure)

The withdrawal procedure is the same as that described above for FIGS. 5-8.

(3) Payment Procedure

FIGS. 45-49 show a diagrammatic representation of the payment protocol. Referring to FIG. 46, the user encryption program encrypts the digital cash token [x,Rd]SKI and the digital cash issuer license [pPKU]SKI using the public key of the shop PKS, and sends the encrypted information to the shop as request for payment.

The user can send a payment request using another certified pseudonym public key, because the pseudonym is not associated with digital cash token. As a result, the pseudonym may be changed at the time of payment thereby increasing user payment options.

The shop decryption program decrypts the encrypted digital cash token and the digital cash issuer license PKS([x,Rd]SKI, [pPKU]SKI) using the shop's secret key SKS. The signature verifying program verifies the signature of the issuer with the digital cash issuer public key PKI. If the signatures are valid, the shop encryption program encrypts the digital cash token [x,Rd]SKI, the user's digital cash issuer license [pPKU]SKI, and the shop identification SID using the public key of the digital cash issuer PKI, and sends the encrypted digital cash token PKI([x,Rd]SKI, [pPKU]SKI, SID) to the digital cash issuer via a communications path.

Referring to FIG. 47, the digital cash issuer decryption program decrypts the encrypted digital cash token PKI([x,Rd]SKI, [pPKU]SKI, SID) using the secret key of the digital cash issuer SKI. The signature verifying program verifies the validity of the digital cash token using the digital cash issuer's public key PKI. If the signature is valid, the digital cash issuer determines whether the token has already been spent. If the token has not been spent, the random number is deleted. The digital cash issuer signature generating program signs the shop identification SID and the amount of digital cash x with the digital cash issuer's secret key SKI and stores [SID,x]SKI temporarily, to send it to the shop's bank. The encryption program encrypts the information using the public key of the shop PKS, and sends the encrypted information PKS([SID,x]SKI) to the shop via a communications path.

The shop receives PKS([SID,x]_(SKI)) and the decryption program decrypts the information using the secret key SKS. The signature verifying program verifies the signature with the public key of the issuer PKI. Referring to FIG. 48, if the signature is valid, the shop random number generating program generates a random number Rs then the signature generating program signs Rs with the shop's secret key SKS. The encryption program encrypts the signed random number [Rs]_(SKS) using the user's pseudonym public key pPKU and sends pPKU([Rs]_(SKS)) to the user via a communications path.

The user receives pPKU([Rs]_(SKS)) and the decryption program decrypts it using the user's pseudonym secret key pSKU and stores [Rs]_(SKS) in the storage device.

Referring to FIG. 49 the digital cash issuer retrieves the signed shop identification SID and the signed amount x to be deposited for the shop [SID,x]_(SKI), and the encryption program encrypts the information by using the public key of the shop's bank PKB before it sends PKB([SID,x]_(SKI)) to the shop's bank via a communications path.

The shop's bank receives PKB([SID,x]_(SKI)), and the decryption program decrypts the information using the secret key SKB. The signature verifying program verifies the signature with the public key of the issuer PKI. If the signature is valid, the shop's bank adds the amount of money x to the shop account.

Eighth Embodiment

This is an on-line protocol with the use of a cryptographic coprocessor.

(1) User Registration Procedure

The user registration procedure for this example is the same as described above for FIGS. 2, 3, and 4.

(2) Withdrawal Procedure (Electronic Cash Issuing Procedure)

The withdrawal procedure for this example is the same as described above for FIGS. 13-16.

(3) Payment Procedure

The payment procedure for this example is the same as described above for FIGS. 45-49.

Ninth Embodiment

This is an online protocol with a mobile device.

(1) User Registration Procedure

The user registration procedure for this example is the same as described above for FIGS. 2, 3, and 4.

(2) Withdrawal Procedure (Electronic Cash Issuing Procedure)

The withdrawal procedure for this example is the same as described above for FIGS. 17-22.

(3) Payment Procedure

FIGS. 50-55 show a diagrammatic representation of the payment protocol. Referring to FIGS. 50 and 51, the user's mobile device chooses the value of the digital cash token x, and the encryption program encrypts the value and the user's pseudonym public key pPKU using the mobile/home shared secret key MHS. The mobile device sends the encrypted information MHS(pPKU,x) to the user's home station via a communications path.

The user's home station receives the encrypted information MHS(pPKU,x), and the decryption program decrypts the information using the mobile/home shared secret key MHS. The user's home station determines if user's pseudonym public key matches the decrypted pseudonym public key to authenticate the user's mobile based device. If the user's pseudonym public key matches, the mobile device is authenticated and the user's home station finds the digital cash token that is equivalent to the value that is sent by the user's mobile device.

Referring to FIG. 52, the user's home station encryption program encrypts the digital cash token [x,Rd]SKI and the digital cash issuer license [pPKU]SKI using the public key of the shop PKS. The user's home station sends the encrypted information to the shop via a communications path as request for payment.

The user's home based station can send a payment request using another certified pseudonym public key, because the pseudonym is not associated with digital cash token. As a result, the pseudonym may be changed at the time of payment thereby increasing user payment options.

The shop decrypts decryption program the encrypted digital cash token and the digital cash issuer license PKS([x,Rd]SKI, [pPKU]SKI) using the shop's secret key SKS. The signature verifying program verifies the signature of the issuer with the digital cash issuer public key PKI. If the signature is valid, the shop encryption program encrypts the digital cash token [x,Rd]SKI, the user's digital cash issuer license [pPKU]SKI, and the shop identification SID using the public key of the digital cash issuer PKI, and sends the encrypted digital cash token PKI([x,Rd]SKI, [pPKU]SKI, SID) to the digital cash issuer via a communications path.

Referring to FIG. 53, the digital cash issuer decryption program decrypts the encrypted digital cash token PKI([x,Rd]SKI, [pPKU]SKI, SID) using the secret key of the digital cash issuer SKI. The signature verifying program verifies the validity of the digital cash token using the digital cash issuer's public key PKI. If the signature is valid, the digital cash issuer determines whether the token has already been spent. If the token has not been spent, the random number is deleted, and the digital cash issuer signature generating program signs the shop identification SID and the amount of digital cash x with the digital cash issuer's secret key SKI. The cash issuer then stores [SID,x]SKI temporarily, to send it to the shop's bank, and the encryption program encrypts the information using the public key of the shop PKS, then sends the encrypted information PKS([SID,x]SKI) to the shop via a communications path.

The shop receives PKS([SID,x]_(SKI)), and the decryption program decrypts the information using the secret key SKS. The signature verifying program verifies the signature with the public key of the issuer PKI. Referring to FIG. 54, if the signature is valid, the shop random number generating program generates a random number Rs and the signature generating program signs Rs with the shop's secret key SKS. The encryption program encrypts the signed random number [Rs]_(SKS) using the user's pseudonym public key pPKU and sends pPKU([Rs]_(SKS)) to the user station via a communications path.

The user station receives pPKU([Rs]_(SKS)). The decryption program decrypts the information using the user's pseudonym secret key pSKU and stores [Rs]_(SKS) in the storage device.

Referring to FIG. 55, the digital cash issuer retrieves the signed shop identification SID and the signed amount x to be deposited for the shop [SID,x]_(SKI). The encryption program encrypts the information using the public key of the shop's bank PKB and sends PKB([SID,x]_(SKI)) to the shop's bank via a communications path.

The shop's bank receives PKB([SID,x]_(SKI)), and the decryption program decrypts the information by using the secret key SKB. The signature verifying program verifies the signature with the public key of the issuer PKI. If the signature is valid, the shop's bank adds the amount of money x to the shop account.

Tenth Embodiment

According to this embodiment an online protocol is provided with untraceable cash tokens. Traceability may be avoided by eliminating the registration phase. In this case, the user can spend digital cash tokens without any reference to the digital cash issuer; however, the protocol still guarantees that no double spending takes place. As a result, the protocol includes two stages.

(1) Withdrawal Procedure (Electronic Cash Issuing Procedure)

FIGS. 56-59 show a diagrammatic representation of the withdrawal protocol. Referring to FIG. 57, the user encryption program encrypts the random shared secret key SH and the amount of digital cash x using the digital cash issuer's public key PKI. The signature generating program signs the user real identification UID, the amount of money to be withdrawn x, the encrypted random shared secret key SH, and the amount of digital cash x PKI(SH,x) using the user's master secret key mSKU. The user encryption program encrypts the information using the public key of the user's bank PKB, and sends the encrypted information PKB([PKI(SH,x),UID,x]mSKU) to the user's bank via a communications path.

The user's bank decryption program decrypts the information PKB([PKI(SH,x),UID,x]mSKU) using the user's bank's secret key SKB. The signature verifying program verifies the validity of the signature for authentication with the master public key of the user mPKU. If the signature is valid, the bank withdraws the amount of money x from the user account, and the signature generating program signs the encrypted random shared secret key SH, the amount of digital cash x PKI(SH,x), and the withdrawn amount of money x using the user's bank's secret key SKB. The bank encryption program encrypts the information using the public key of the digital cash issuer PKI, and sends the encrypted information PKI([PKI(SH,x),x]SKB) to the digital cash issuer via a communications path.

Referring to FIG. 58, the digital cash issuer receives PKI([PKI(SH,x),x]SKB). The decryption program decrypts the information using the digital cash issuer's secret key SKI. The signature verifying program verifies the signature of the bank using the public key of the bank PKB. If the signature is valid, the digital cash issuer decryption program decrypts the information PKI(SH,x) using the digital cash issuer's secret key. The issuer verifies the equality of the two amounts x. If the amounts are not equal, the process aborts. If the amounts are equal, the digital cash issuer issues a digital cash token that includes the following information: (i) digital cash amount, and (ii) random number. The digital cash issuer generates a random number Rd and stores the random number in its storage device. The signature generating program signs digital cash amount x and random number Rd using the digital cash issuer's secret key SKI. The encryption program encrypts the information using the random shared secret key SH that was provided by the user. The signature generating program signs the encrypted digital cash token SH([x,Rd]SKI) using the digital cash issuer's secret key SKI. The encryption program encrypts the signed, encrypted digital cash token [SH([x,Rd]SKI)]SKI using the public key of the user's bank PKB, and sends PKB([SH([x,Rd]SKI)]SKI) to the user's bank via a communications path.

Referring to FIG. 59, the user's bank receives the information PKB([SH([x,Rd]SKI)]SKI) and the decryption program decrypts the information using the user's bank secret key SKB. The signature verifying program verifies the digital cash issuer signature using the public key of the digital cash issuer PKI. If the signature is valid, the issuer sends the encrypted digital cash token SH([x,Rd]SKI) to the user via a communications path.

The user receives the encrypted digital cash token SH([x,Rd]SKI), and the decryption program decrypts the encrypted digital cash token using the random shared key SH. The signature verifying program verifies the validity of the digital cash issuer signature with the digital cash issuer's public key PKI. If the signature is valid, the digital cash token [x,Rd]SKI is stored in the storage device of the user.

According to this embodiment, the user can easily transfer the issued digital cash token to another user who has a certified pseudonym public key.

(2) Payment Procedure

FIGS. 60-64 show the diagrammatic representation of the payment protocol. Referring to FIG. 61, the user encryption program encrypts the digital cash token [x,Rd]SKI and a random shared secret key SH using the public of the shop PKS then sends it to the shop as request for payment.

The shop decryption program decrypts the encrypted digital cash token and the random shared secret key PKS([x,Rd]SKI,SH) using the shop's secret key SKS. The signature verifying program verifies the signature of the issuer with the digital cash issuer public key PKI. If the signature is valid, the shop stores the random shared secret key temporally in its storage device, and the encryption program encrypts the digital cash token [x,Rd]SKI and the shop identification SID using the public key of the digital cash issuer PKI. The encrypted digital cash token PKI([x,Rd]SKI, SID) is then sent to the digital cash issuer via a communications path.

Referring to FIG. 62, the digital cash issuer decryption program decrypts the information PKI([x,Rd]SKI, SID) using the secret key of the digital cash issuer SKI. The signature verifying program verifies the validity of the digital cash token using the digital cash issuer's public key PKI. If the token is valid, the digital cash issuer determines whether the token has already been spent. If the token has not been spent, the random number is deleted, and the digital cash issuer signature generating program signs the shop identification SID and the amount of digital cash x with the digital cash issuer's secret key SKI. The digital cash issuer stores signed shop identification and amount [SID,x]SKI temporarily, to send it to the shop's bank, and the encryption program encrypts the information using the public key of the shop PKS. The encrypted information PKS([SID,x]SKI) is then sent to the shop via a communications path.

Referring to FIG. 63, the shop receives the encrypted information PKS([SID,x]SKI), and the decryption program decrypts the information using the secret key SKS. The signature verifying program verifies the signature with the public key of the issuer PKI. If the signature is valid, the shop random number generating program generates a random number Rs, and the signature generating program signs Rs with the shop's secret key SKS. The encryption program encrypts the signed random number [Rs]SKS using the user's random shared secret key SH, and sends SH([Rs]SKS) to the user via a communications path.

The user receives the encrypted information SH([Rs]SKS), and the decryption program decrypts the information using the random shared secret key SH. The user stores the signed random number [Rs]SKS in its storage device.

Referring to FIG. 64, the digital cash issuer retrieves the signed shop identification SID and the signed amount x to be deposited for the shop [SID,x]SKI. The encryption program encrypts the information using the public key of the shop's bank PKB, and sends the encrypted information PKB([SID,x]SKI) to the shop's bank via a communications path.

The shop's bank receives the encrypted information PKB([SID,x]SKI), and the decryption program decrypts the information using the secret key SKB. The signature verifying program verifies the signature with the public key of the issuer PKI. If the signature is valid, the shop's bank adds x amount of money to the shop account.

As mentioned, most of the conventional virtual account based digital cash protocols use blind signature to protect the privacy of the user which is not efficient and is vulnerable to fraud. In addition, some offline protocols do not use blind signature but still have deficiency in privacy protection and deficiency in authentications. The protocol provided herein may be implemented in a virtual account based digital cash system that provides: (i) strong protection of user's privacy (ii) authenticated protocol, (iii) traceability, and (iv) achieving all of these without using blind signature schemes.

The protocols described above provide strong protection of privacy for the user by separating information about the user's bank accounts (identified with the real identity of the user) from the information about digital cash tokens of the same user under a pseudonym by using two pair of keys where one pair is linked to the real identity of the user, while the other pair is linked to the pseudonym identity of the user. The use of the two pair of keys allows the users to use one pair of keys for authenticating the user with an entity that holds information that is linked to the user's real identity, and for encrypting information sent to the user by such entities. At the same time, the user can use another pair of keys to authenticate the user with an entity that holds information that is linked to the user's pseudonym identity such as an issuer of digital cash tokens, and for encrypting information sent to the user by such entities.

Because there is no link between the master public key of the user with the pseudonym public key of the same user, there is no link between the real identity of the user and the user's pseudonym. The only exception to this is a certificate authority which certifies the pseudonym public key of a user given a user's master public key and id. There is no shared information about the user between the user's bank and the issuer of digital cash virtual accounts. This separation makes it very difficult to link the real identity of the user with the user's pseudonym pubic key. Any leak of the private key of the bank or the issuer of digital cash virtual accounts is useless to break the privacy of the user. Since the user's master public key is not linked to digital cash token and is not used for payments, the user's privacy is maintained. Therefore, strong protection is provided to maintain the user privacy without involving any blind signature scheme.

In the protocols described above, the user has two pair of keys wherein one pair represents master keys while the other pair represents pseudonym keys and wherein each public key is certified by a certifying authority using a separate certificate. Digital signatures with master keys are used for authentication with the certificate authority and the bank, wherein digital signatures with pseudonym keys are used for authentication with the issuer of digital cash virtual accounts and the shop. Since all transactions are authenticated using digital signatures, this prevents anyone from pretending to be someone else by providing information related to the real user.

A number of exemplary implementations have been described. Nevertheless, it will be understood that various modifications may be made. For example, suitable results may be achieved if the steps of described techniques are performed in a different order and/or if components in a described system, architecture, device, or circuit are combined in a different manner and/or replaced or supplemented by other components. Accordingly, other implementations are within the scope of the following claims. 

1. A system for implementing a digital cash token protocol, the system comprising: a user having two pairs of user keys, one pair linked to the real identity of the user, and a second pair linked to the pseudonym identity of the user, a bank to receive a request for an amount of digital cash from the user and generate a request for a digital cash token corresponding to the requested amount; and an issuer of digital cash to issue the digital cash token in response to the request from the bank, wherein the first pair of keys is used to authenticate the user with the bank and to encrypt information sent to the user from the bank and the second pair of keys is used to authenticate the user with the issuer of digital cash and to encrypt information sent to the user from the issuer of digital cash.
 2. The system of claim 1 wherein the first pair includes a master public key and a master secret key and the second pair includes a pseudonym public key and a pseudonym secret key.
 3. The system of claim 2 wherein no link is provided between the master public key and the pseudonym public key to determine the real identity of a user associated with a pseudonym.
 4. The system of claim 2 further comprising a certificate authority to certify the pseudonym public key of a user given the master public key of the user and a user identification.
 5. The system of claim 2 wherein no link is provided between the master public key and the issued digital cash token, and the master public key is not used for payments in order to maintain user privacy.
 6. The system of claim 4 wherein each public key is certified by the certificate authority using a separate certificate.
 7. The system of claim 6 wherein the user may transfer the issued digital cash token to another user that has a certified pseudonym public key.
 8. The system of claim 2 wherein the master keys are used to generate digital signatures for authentication with the certificate authority and the bank.
 9. The system of claim 2 wherein pseudonym keys are used to generate digital signatures for authentication with the issuer of digital cash.
 10. The system of claim 4 wherein the certificate authority stores the pseudonym public key in correspondence to a user id or the master public key and issues a license for the pseudonym public key in response to a request which is signed by the master private key of the user.
 11. The system of claim 10 wherein the certificate authority reveals the identity of the owner of a pseudonym public key if there is any misuse of digital cash token.
 12. The system of 1 wherein the issuer of digital cash tokens issues a digital cash license to the user and stores information related to the issued digital cash token.
 13. The system of claim 12 wherein the stored information related to the issued digital token includes a random number. 14-32. (canceled) 